Mobile Application Development Device

ABSTRACT

A mobile application development device having a platform processor, a native application converter engine, and a mobile platform framework engine configured to facilitate the development and deployment of mobile applications configured to be run on different mobile operating systems from code that is developed independently and agnostic of the mobile operating system on which it will ultimately run.

This application claims the benefit of and is a continuation of U.S.Pat. Application Serial No. 17/839,067, filed Jun. 13, 2022 and entitled“Mobile Application Development Device,” which is continuation of U.S.Pat. Application Serial No. 17/398,758, filed Aug. 10, 2021, andentitled “Mobile Application Development Device,” both of which areincorporated by reference herein in their entireties,

TECHNICAL FIELD

Aspects of this disclosure generally relate to processes and devicesutilized in mobile application development. This disclosure includes adevice that can be used to allow application development to be agnosticto the type of mobile operating system on which the applicationfunctionality will ultimately be implemented.

BACKGROUND

Mobile application development within an organization may involveimplementing a project as multiple different versions of an applicationtailored to different mobile operating systems, and tailored todifferent types of users (internal users within an organization, andpublic users external to an organization, among others). Thisdevelopment methodology may introduce inefficiencies associated withrecreating functions for each application type. No device exists thataddresses these development inefficiencies that can be used tostreamline mobile application development.

BRIEF SUMMARY

In light of the foregoing background, the following presents asimplified summary of the present disclosure in order to provide a basicunderstanding of some aspects of the various implementations of thisdisclosure. This summary is not an extensive overview of the embodimentsdescribed herein. It is not intended to identify key or criticalelements, or to delineate the scope of the embodiments described in thisdisclosure. The following summary merely presents some concepts of theembodiments of this disclosure in a simplified form as a prelude to themore detailed description provided below.

In one aspect, this disclosure includes a mobile application developmentdevice that includes a platform processor. The platform processor may beconfigured to identify an application build element of an application indevelopment, identify and classify an application logic block portion ofthe application build element written in a platform-agnostic language,and identify a platform on which application is to be executed. Theplatform processor may further be configured to apply a platform-nativetemplate to the application logic block that is specific to the platformon which application is to be executed. The mobile applicationdevelopment device may further include a native application converterengine that is configured to identify logic features that are specificto the application to be built, and to extract the logic features as afirst set of tags associated with the application to be built. Thenative application converter engine may also be configured to identify asecond set of tags within the template applied by the platformprocessor, such that the second set of tags matches the first set oftags. The native application converter engine may further be configuredto replace the second set of tags with elements that are specific to theapplication to be built, and output a converted intermediary codebase.The mobile application development device may also include a mobileplatform framework engine that is configured to add a common set ofapplication features to the converted intermediary codebase, such thatsubsequent to the addition of the common set of application features,the converted intermediary codebase is compiled and outputted as theapplication.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. The Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and is notlimited in the accompanying figures in which like reference numeralsindicate similar elements.

FIG. 1 schematically depicts a mobile application development device,according to one or more aspects described herein;

FIG. 2 schematically depicts another implementation of a mobileapplication development device, according to one or more aspectsdescribed herein;

FIG. 3 is a flowchart diagram of a process for efficient development ofa mobile application suitable for execution on multiple different mobileoperating systems, according to one or more aspects described herein;

FIG. 4 schematically depicts a flowchart diagram of a process tofacilitate two-phase development of cross-platform mobile applicationsusing an application data transformation processor, according to one ormore aspects described herein;

FIG. 5 schematically depicts the application data transformationprocessor, according to one or more aspects described herein; and

FIG. 6 shows an illustrative operating environment in which variousaspects of the disclosure may be implemented, according to one or moreaspects described herein.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

Various connections between elements are discussed in the followingdescription. It is noted that these connections are general and, unlessotherwise specified, may be direct or indirect, wired or wireless, andthat the specification is not intended to be limiting in this respect.

FIG. 1 schematically depicts a mobile application development device102, according to one or more aspects described herein. It iscontemplated that the mobile application development device 102 may beimplemented as one or more hardware elements that include one or moreapplication-specific integrated circuits. In other examples, the mobileapplication development device 102 may additionally or alternativelyinclude software and/or firmware elements in order to implement thefunctionality described herein. Further examples of implementations ofthe mobile application development device 102 are presented inproceeding sections of this disclosure. It is further contemplated thatthe mobile application development device 102 may use any machinelearning and/or deep learning processes that utilize supervised orunsupervised learning. As such, machine learning and deep learning maybe used interchangeably in the description that follows.

The mobile application development device 102 may be utilized tofacilitate efficient development of mobile applications suitable forexecution on multiple different mobile operating systems.Advantageously, the mobile application development device 102 may allowfor applications to be coded using one or more languages that areagnostic to the ultimate mobile operating system on which they will berun, such that developers can build functionality of an application thatcan be implemented on multiple different mobile operating systems. Inone example, App Code A 104, App Code B 106, and App Code C 108schematically represent blocks of code that define the functionality ofthree distinct applications. Elements 104-108 may alternatively bereferred to as application build elements, blocks of code, orapplication builds, among others. App Code A 104, App Code B 106, andApp Code C 108 may be coded using a general-purpose coding language thatis not specific to any mobile operating system. Further, App Code A 104,App Code B 106, and App Code C 108 may use a same or different codinglanguages.

In one example, each of App Code A 104, App Code B 106, and App Code C108 may be maintained/ coded by a separate team within an organization,and each may represent a different mobile application with functionalitythat is intended to be run as a mobile application on differentoperating systems, and at different priority levels. For example, agiven application may ultimately be implemented on two or more differentmobile operating systems, and may be published as both an internalapplication and a public-facing application, whereby access permissionsmay differ between the internal and public facing application.Accordingly, the mobile application development device 102 mayfacilitate automated building of different versions of an applicationintended to be run on different mobile operating systems and asdifferent build types (e.g. internal-facing and public-facing) from codethat is written in a programming language that is agnostic to theoperating system on which the application will ultimate may be run(e.g., from App Code A 104, App Code B 106, or App Code C 108). In oneexample, the App Code A 104, App Code B 106, and App Code C 108 blocksmay be referred to as blocks of “business code,” indicating that thefunctionality described by the App Code A 104, App Code B 106, and AppCode C 108 blocks may concentrate on specific business functions, ratherthan details specific to a given mobile operating system or specific tocommunication and/or security elements.

In one example, one or more of the App Code A 104, App Code B 106, andApp Code C 108 blocks may include an application logic block, or “applogic block 105.” This app logic block 105 may include code describingone or more subcomponents of a broader/bigger application represented byApp Code A 104, or another block of code. It is contemplated that theapplications, and the subcomponents thereof represented by App LogicBlock 105, may include any functionality, without departing from thescope of these disclosures. In certain examples, one or more of the AppCode A 104 and the App Logic Block 105 may identify an application typethat is to be built and published, including operating system on whichthe application is intended to be run, and/or a priority levelassociated with the application, which may indicate whether theapplication is to be an internal application, or a publicly availableapplication.

In one example, the mobile application development device 102 mayinclude a platform processor 110. The platform processor 110 may beconfigured to identify an application build element of an applicationand development, such as, in one example, App Code A 104, App Code B106, and/or App Code C 108. The platform processor 110 may additionallybe configured to identify and to classify an application logic blockportion, such as App Logic Block 105. This classification may includeidentification of functionality associated with the application logicblock, an intended mobile operating system on which the application isto be run, security features associated with/required as result offunctionalities of the planned application, access permissionsassociated with the application to be built, user interface featuresassociated with the application to be built, communication channelsrequired by the application, among others.

In one example, the platform processor 110 may identify a platform onwhich an application associated with App Code A 104, App Code B 106,and/or App Code C 108 it is to be executed. This identification of aplatform may include, among others, identifying elements within the codeindicating a mobile operating system or other characteristics of theapplication to be built, such as a prioritization of the application asa high priority application build or a medium or low priorityapplication build. The identification of a platform may also include anindicator of an application type in addition to a mobile operatingsystem on which the application is intended to be executed. Theapplication type information may include details on whether theapplication will be for internal customers within an organization, orwhether the application will be available to external customers outsideof the organization as a publicly available application. In one example,the platform processor 110 may receive information on the applicationtype and platform on which the application is to be executed as separateinformation received from a user and separate to the App Code A 104, AppCode B 106, and/or App Code C 108.

The platform processor 110 may be further configured to apply aplatform-native template to an application logic block, such as block105. This platform-native template may be specific to the platform onwhich the application is to be executed, such as a specific mobileoperating system platform. Platform Native Template A 112 and PlatformNative Template B 114 are two examples of templates that may be appliedto App Logic Block 105 (or other blocks or whole application buildsassociated with App Code A 104, App Code B 106, and/or App Code C 108).Templates 112 and 114 may each be associated with a specific mobileoperating system, and apply/ convert elements of the coding of App CodeA 104, App Code B 106, and/or App Code C 108 that are written in aplatform-agnostic language to code that is suitable for building andpublishing as an application for a specific mobile operating system.Accordingly, the platform processor 110 may facilitate hybriddevelopment of a mobile application such that App Code A 104, App Code B106, and/or App Code C 108 can be written/constructed by personnel in adesktop environment without requiring the testing of applicationfunctionality on a mobile device, and/or without specific knowledge ofcoding for a mobile device. Advantageously, mobile applicationdevelopment device 102 may allow the functionality, or “business code”of the App Code A 104, App Code B 106, and/or App Code C 108 to beseparated from the specifics of implementing an application on a mobiledevice with adequate functionality specific to the mobile device, withrobust security functionality, and with interconnectivity to otherapplications/ databases/ features of an organization within which theapplications are being developed. The platform processor 110 may includeone or more libraries of code elements associated with a platform onwhich the application is intended to run. For example, the platformprocessor 110 may include two separate libraries of code elementsspecific to each of the platforms associated with templates 112 andtemplate 114.

The mobile application development device 102 may additionally include anative application converter engine 116. This native applicationconverter engine 116 may be configured to execute one or more processesto identify logic features that are specific to an application to bebuilt, and extract the logic features as a first set of tags associatedwith the application to be built. In one implementation, theidentification of the logic features may include identification offeatures within an application logic block, such as block 105. In oneexample, this first set of tags may include application characteristicssuch as an application name, a unique identifier for the application,application icons, images, signatures, network security features,notification features, user interface features, among many others. Thefirst set of tags may be extracted from App Code A 104, App Code B 106,and/or App Code C 108. In one example, the native application converterengine 116 may build native shells specific to a mobile operating systemon which the application is to be run, and dynamically build thesemobile operating system-specific shells dynamically during a buildprocess based upon an application configuration. The extracted first setof tags may be stored within a tag database 118. It is contemplated thatany database structure may be utilized for database 118 or any otherdatabase within this disclosure, without departing from the scope ofthese disclosures.

The native application converter engine 116 may additionally include oneor more processes configured to identify a second set of tags within thetemplate applied by the platform processor 110 (e.g., template 112 or114). This second set of tags may correspond to/ partially or whollymatch the first set of tags identified within the application codeassociated with App Code A 104, App Code B 106, and/or App Code C 108.

In one example, the native application converter engine 116 may includea native configuration 119. This native configuration 119 may includeelements that are to be inserted into one or more of the App Code A 104,App Code B 106, and/or App Code C 108 in order to prepare theapplication code for implementation on a specific mobile operatingsystem. Accordingly, the native configuration 119 may be includefeatures that are specific to a mobile operating system type, and/orapplication prioritization type (e.g., high, medium, or low priorityapplication, internally facing or publically available application,among others). In one example, the native configuration 119 may includeelements that are configured to replace the values associated with thesecond set of tags. The native application converter engine 116 mayoutput a converted intermediary codebase 120 upon replacing the secondset of tags with the values stored in the native configuration 119. Thisconverted intermediary codebase 120 may then be communicated to a mobileplatform framework engine 122.

In one example, the mobile platform framework engine 122 may beconfigured to add a common set of application features to the convertedintermediary codebase 120. This common set of application features mayinclude functional elements that are used in multiple or allapplications built by an organization, such as user interface elements(navigation bars, artwork, logos, images, standard text such asdisclaimers, among many others), network communication elements,notification features, security features (SSO, certificates, amongothers). In one example, the features applied by the mobile platformframework engine 122 may be stored in app feature set 124. It iscontemplated that any storage structure may be utilized with element124, without departing from the scope of these disclosures.

An application compiler 126 may be utilized to compile the codeoutputted from the mobile platform framework engine 122 once the commonset of application features has been added to the converted intermediarycodebase 120. This compiler 126 may be implemented as any suitablecompiler element, device, and/or application, without departing from thescope of these disclosures. Further, a compiled application outputtedfrom the application compiler 126 may be received by a publishing engine128. The publishing engine 128 may be configured to publish theapplication on an internal, or external repository for applications suchthat the application may be accessed and downloaded to mobile devices aspublished application 150.

FIG. 2 schematically depicts another implementation of a mobileapplication development device 202, according to one or more aspectsdescribed herein. In certain examples, the mobile application developerdevice 202 may otherwise be referred to as a two-phase applicationdeveloper device 202, according to one or more aspects described herein.The two phases of mobile application development may be associated witha first phase implemented using a browser-based application developmentdevice/software, and a second phase implemented on a mobile device. Themobile application development device 202 may be similar to device 102,such that like elements are represented by the same numbers. Inaddition, the mobile application development device 202 includes anapplication data transformation processor 125. Advantageously, theapplication data transformation processor 125 is configured tofacilitate two-phase development of cross-platform mobile applications.In one example, the first phase of the cross-platform mobile applicationdevelopment includes development of the business code associated withApp Code A 104, App Code B 106, and/or App Code C 108 within a desktopenvironment using one or more programming languages that are agnostic toone or more specific languages and/or application features required by amobile operating system on which an application is ultimately configuredto be run. Alternatively, the first phase may be a web-based engineconfigured to emulate a mobile operating system. Further, the secondphase of the cross-platform mobile application development may includefinalization of the mobile application using a mobile simulator ordirectly on a mobile device. Advantageously, the application datatransformation processor 125 facilitates this two-phase development byautomatically implementing appropriate communication channels such thatsuitable communication can be established on the mobile application, andwithout requiring a developer building one or more of App Code A 104,App Code B 106, and/or App Code C 108 to be aware of the specifics ofthe required communication channels. In certain examples, thecommunication channels implemented by the application datatransformation processor 125 may facilitate communication to one or moresecure databases, applications, networks, browsers, mobile simulators ormobile devices, among other elements. It is contemplated that theapplication data transformation processor 125 may be configured toconnect using any network communication protocol or channel (such as avirtual private network (VPN), among many others), and utilizing anysuitable encryption or security protocol.

In one example, the application data transformation processor 125 may beconfigured to identify a communication request type, to select anappropriate network channel to fulfill the communication request, and toset up a communication session using an appropriate network channel tothe requested destination. In one example, the communication session setup by the application data transformation processor 125 may bepersistent or temporary, and may be obfuscated from a requesterassociated with the communication request type, such that the App Code A104, App Code B 106, and/or App Code C 108 can be configured to retrievedata of differing types without specific knowledge of the data channelsrequired to access the requested data. In one example, the applicationdata transformation processor 125 may be configured to identify a sourceof a request as a desktop environment (it is contemplated that a desktopenvironment may refer to any application development efforts implementedon a non-mobile operating system, such that the hardware may include adesktop computer, a laptop computer, among others), a web browser, or amobile device, and apply different communication strategies based onthis identification. Accordingly, processor 125 may be configured toadapt as an application in development is migrated from being developedon a desktop/browser-based platform to being finalized or implemented ona mobile device. Accordingly, the application data transformationprocessor 125 may automatically update communication links within anapplication based upon the source of the request being a desktopenvironment, a web browser or a mobile device.

FIG. 3 is a flowchart diagram 300 of a process for efficient developmentof a mobile application suitable for execution on multiple differentmobile operating systems. One or more processes may be executed at block302 to identify an application build element, such as App Code A 104,App Code B 106, and/or App Code C 108. These one or more processes maybe executed by the platform processor 110. Further, one or moreprocesses may be executed at block 304 to identify an application logicblock portion, such as logic block 105. This logic block portion may bewritten in a platform-agnostic programming language. It is contemplatedthat any programming languages may be utilized with the systems andmethods described herein. In one example, the one or more processesexecuted at block 304 may be executed by the platform processor 110.

In one example, and at block 306, one or more processes may be executedto identify a platform on which an application is to be executed. Theseone or more processes may additionally identify an application typeand/or priority type. Further, block 306 may be executed by the platformprocessor 110. At block 308, the platform processor 110 may execute oneor more processes to apply a platform-native template to an applicationlogic block.

One or more processes may be executed at block 310 to identify logicfeatures that are specific to the application to be built. These logicfeatures may be identified by the native application converter engine116. Further, one or more processes may be executed to extract the logicfeatures as a first set of tags associated with the application to bebuilt at block 312, and executed by the native application converterengine 116. One or more processes may be executed at block 314 toidentify a second set of tags within the template applied by theplatform processor 110 that matches the first set of tags. Further, thesecond set of tags may be replaced with elements that are specific tothe application to be built. This replacing may be executed by thenative application converter engine 116, to result in a convertedintermediary codebase 120.

Further, and at block 318, one or more processes may be executed to adda common set of application features. This addition of the common set ofapplication features may be executed by the mobile platform frameworkengine 122. Subsequently, one or more processes may be executed tocompile and publish the application at block 320, such that thecompiling and publishing may be executed by the compiler 126 andpublishing engine 128.

FIG. 4 schematically depicts a flowchart diagram 400 of a process tofacilitate two-phase development of cross-platform mobile applicationsusing an application data transformation processor, according to one ormore aspects described herein. In one example, one or more processes maybe executed at block 402 to receive the converted intermediary codebase120. In one example, the converted intermediary codebase 120 may bereceived by the mobile application framework engine 122, andspecifically by the application data transformation processor 125. Oneor more processes may be executed at block 404 to identify acommunication request type from the received intermediary codebase 120.These one or more processes executed at block 404 may be executed by theapplication data transformation processor 125, and may include anidentification of a request for information from a database, request foraccess to an internal or external network, a request for access tosecurity certificates, a request for another application or a website orweb-hosted application features, among many others.

The application data transformation processor 125 may be configured toselect an appropriate network channel based upon one or more features ofan application associated with App Code A 104, App Code B 106, and/orApp Code C 108. For example, one or more processes may be executed atblock 406 to select an appropriate network channel based upon identifiedconnectivity requirements of an application to be built by the mobileapplication development device 202. The network channel selected atblock 406 may be specific to the phase of development such that theapplication data transformation processor 125 may select a first networkchannel when the application is in an early stage of development(phase 1) and is being developed within a desktop/web environment, andmay automatically select a second network channel when the applicationis in a later stage of development (phase 2) and being tested orimplemented on a mobile device. Accordingly, the application datatransformation processor 125 may provide for seamless communicationcontinuity such that upstream development can request information fromone or more sources without defining the specific communication channelsthat are to be used to obtain the requested information. In one example,the application data transformation processor 125 may utilize aninternal network to facilitate communication between a requestingapplication and a source of the requested information (which may be adatabase, a website among others) when an application is being developedwithin a desktop/web-based development environment, and may utilize avirtual private network to facilitate the same information retrievalwhen the application is implemented on a mobile device. Accordingly, oneor more processes may be executed by the application data transformationprocessor 125 at block 408 to set up a communication session tofacilitate the requested data type on the selected network channel.

FIG. 5 schematically depicts the application data transformationprocessor 125. In one example, the application data transformationprocessor 125 includes a transport roadmap 501. This transport roadmap501 may include a database of communication channel types associatedwith different request sources and destinations for example, the roadmap501 may include a store of primary, secondary, and tertiarycommunication channels sorted based upon the type of informationrequested, the type of requester (e.g. a request from an application inphase 1 of development on a desktop/web-based platform, or in phase 2 ofdevelopment on a mobile device, among others), a destination address/source. The communication channels may include different communicationprotocols, different hardware types, and different communicationmethodologies. In certain examples, the transport roadmap 501 mayinclude multiple nodes in a communication path, and may include detailsfor setting up secure communication channels, using virtual privatenetworks (VPNs) or other tunneling methodologies, among others. It iscontemplated that the application data transformation processor 125 maybe configured to utilize any communication hardware, firmware, and/orsoftware type, without departing from the scope of these disclosures.Further, the application data transformation processor 125 may beconfigured to connect to different data sources, which may include a webbrowser 502, applications configured to simulate different mobileoperating systems, such as Mobile Simulator A 504

In certain examples, the mobile application development device 102and/or 202 may implement machine learning processes in order toimplement any of the features described herein, such as any of thefeatures described as having automated processes. In certain examples, aframework for machine learning implemented by the device 102 and/or 202may involve a combination of one or more components, which may includethree components: (1) representation, (2) evaluation, and (3)optimization components. Representation components refer to computingunits that perform steps to represent knowledge in different ways,including but not limited to: as one or more decision trees, sets ofrules, instances, graphical models, neural networks, support vectormachines, model ensembles, and/or others. Evaluation components refer tocomputing units that perform steps to represent the way hypotheses(e.g., candidate programs) are evaluated, including but not limited toas accuracy, prediction and recall, squared error, likelihood, posteriorprobability, cost, margin, entropy k-L divergence, and/or others.Optimization components refer to computing units that perform steps thatgenerate candidate programs in different ways, including but not limitedto combinatorial optimization, convex optimization, constrainedoptimization, and/or others. In some embodiments, other componentsand/or sub-components of the aforementioned components may be present inthe system to further enhance and supplement the aforementioned machinelearning functionality.

Machine learning algorithms sometimes rely on unique computing systemstructures. Machine learning algorithms may leverage neural networks,which are systems that approximate biological neural networks (e.g., thehuman brain). Such structures, while significantly more complex thanconventional computer systems, are beneficial in implementing machinelearning. For example, an artificial neural network may be comprised ofa large set of nodes which, like neurons in the brain, may bedynamically configured to effectuate learning and decision-making.Moreover, machine learning tasks are sometimes broadly categorized aseither unsupervised learning or supervised learning. In unsupervisedlearning, a machine learning algorithm is left to generate any output(e.g., to label as desired) without feedback. The machine learningalgorithm may teach itself (e.g., observe past output), but otherwiseoperates without (or mostly without) feedback from, for example, a humanadministrator.

In an embodiment involving supervised machine learning, a graph modulecorresponding to an artificial neural network may receive and executeinstructions to modify the computational graph. A supervised machinelearning model may provide an indication to the graph module that outputfrom the machine learning model was correct and/or incorrect. Inresponse to that indication, the graph module may modify one or morenodes and/or edges to improve output. The modifications to the nodesand/or edges may be based on a prediction, by the machine learning modeland/or the graph module, of a change that may result an improvement. Themodifications to the nodes and/or edges may be based on historicalchanges to the nodes and/or edges, such that a change may not becontinuously made and unmade (an undesirable trend which may be referredto as oscillation). Feedback may be additionally or alternativelyreceived from an external source, such as an administrator, anothercomputing device, or the like. Where feedback on output is received andused to reconfigure nodes and/or edges, the machine learning model maybe referred to as a supervised machine learning model.

In supervised learning, a machine learning algorithm is providedfeedback on its output. Feedback may be provided in a variety of ways,including via active learning, semi-supervised learning, and/orreinforcement learning. In active learning, a machine learning algorithmis allowed to query answers from an administrator. For example, themachine learning algorithm may make a guess in a face detectionalgorithm, ask an administrator to identify the photo in the picture,and compare the guess and the administrator’s response. Insemi-supervised learning, a machine learning algorithm is provided a setof example labels along with unlabeled data. For example, the machinelearning algorithm may be provided a data set of one hundred photos withlabeled human faces and ten thousand random, unlabeled photos. Inreinforcement learning, a machine learning algorithm is rewarded forcorrect labels, allowing it to iteratively observe conditions untilrewards are consistently earned. For example, for every face correctlyidentified, the machine learning algorithm may be given a point and/or ascore (e.g., “75% correct”).

In one example, a machine learning engine may identify relationshipsbetween nodes that previously may have gone unrecognized, for example,using collaborative filtering techniques. This realization by themachine learning engine may increase the weight of a specific node; andsubsequently spread weight to connected nodes. This may result inparticular nodes exceeding a threshold confidence to push those nodes toan updated outcome from a Boolean false to a Boolean true. Otherexamples of machine learning techniques may be used in combination or inlieu of a collaborative filtering technique.

In addition, one theory underlying supervised learning is inductivelearning. In inductive learning, a data representation is provided asinput samples data (x) and output samples of the function (f(x)). Thegoal of inductive learning is to learn a good approximation for thefunction for new data (x), i.e., to estimate the output for new inputsamples in the future. Inductive learning may be used on functions ofvarious types: (1) classification functions where the function beinglearned is discrete; (2) regression functions where the function beinglearned is continuous; and (3) probability estimations where the outputof the function is a probability.

In practice, machine learning systems and their underlying componentsmay be manually tuned by to perform numerous steps to perfect machinelearning systems. The process is sometimes iterative and may entaillooping through a series of steps: (1) understanding the domain, priorknowledge, and goals; (2) data integration, selection, cleaning, andpre-processing; (3) learning models; (4) interpreting results; and/or(5) consolidating and deploying discovered knowledge. This may furtherinclude conferring with domain experts to refine the goals and make thegoals clearer, given the nearly infinite number of variables that canpossible be optimized in the machine learning system. A framework formachine learning may involve a combination of supervised andunsupervised learning models.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored as computer-readable instructions on a computer-readable mediumsuch as a hard disk, optical disk, removable storage media, solid-statememory, RAM, and the like. The functionality of the program modules maybe combined or distributed as desired in various embodiments. Inaddition, the functionality may be embodied in whole or in part infirmware or hardware equivalents, such as integrated circuits,application-specific integrated circuits (ASICs), field programmablegate arrays (FPGA), and the like. Particular data structures may be usedto more effectively implement one or more aspects of the disclosure, andsuch data structures are contemplated to be within the scope of computerexecutable instructions and computer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may be and/or include one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers and one or more networks. Thefunctionality may be distributed in any manner, or may be located in asingle computing device (e.g., a server, a client computer, and thelike). For example, in alternative embodiments, one or more of thecomputing platforms discussed herein may be combined into a singlecomputing platform, and the various functions of each computing platformmay be performed by the single computing platform. In such arrangements,any and/or all of the above-discussed communications between computingplatforms may correspond to data being accessed, moved, modified,updated, and/or otherwise used by the single computing platform.Additionally or alternatively, one or more of the computing platformsdiscussed above may be implemented in one or more virtual machines thatare provided by one or more physical computing devices. In sucharrangements, the various functions of each computing platform may beperformed by the one or more virtual machines, and any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the one or more virtual machines.

The various elements described throughout this disclosure may beimplemented as standalone hardware elements, or as a combination ofhardware, firmware, and software components. For example, each of theelements of FIG. 1 may be implemented as standalone hardware elementsembodied as application-specific integrated circuits or similar hardwareelements. In another example, two or more of the elements of FIG. 1 maybe combined together and implemented as dedicated hardware elements. Inyet another example, one or more elements of FIG. 1 may be implementedas firmware and/or software modules. Further, one or more of theelements of FIG. 1 may be embodied using a general-purpose orspecialized computing system, such as computing system 600 from FIG. 6 .

As such, the mobile application development device 102, or one or moreof the modules of the device 102 may be implemented as one or morenetwork-linked computer devices, such as device 601 from FIG. 6 . Thus,the mobile application development device 102 may be implemented onconsolidated computing hardware, such as computing device 601, at asingle geographic location, and/or on a single integrated circuit, andthe like. In another example, the mobile application development device102 may be implemented across multiple computing devices at a common, ordispersed geographic locations. In one example, the device 601 may be incommunication with devices 641 and 651 using one or more networkingtechnologies (625, 629, and/or 631) described in further detail in thedescription that follows.

In one example implementation, computing device 601 may have a processor603 for controlling overall operation of device 601 and its associatedcomponents, including RAM 605, ROM 607, an input/output (I/O) module609, and memory 615. In one example, as will be apparent to those ofordinary skill in the art, memory 615 may comprise any known form ofpersistent and/or volatile memory, such as, among others, a hard diskdrive, a solid state disk, optical disk technologies (CD-ROM, DVD,Blu-ray, and the like), tape-based stored devices, ROM, and RAM, orcombinations thereof. In this way, memory 615 may comprise anon-transitory computer-readable medium that may communicateinstructions to processor 603 to be executed.

I/O module 609 may include a microphone, keypad, touch screen, and/orstylus through which a user of the computing device 601 may provideinput, and may also include one or more of a speaker for providing audiooutput and a video display device for providing textual, audiovisualand/or graphical output. Software may be stored within memory 615 and/orstorage to provide instructions to the processor 603 for allowing thecomputing device 601 to perform various functions. For example, memory615 may store software used by the computing device 601, such as anoperating system 617, application programs 619, and an associateddatabase 621. The processor 603 and its associated components may allowthe computing device 601 to run a series of computer-readableinstructions to process and format data.

The computing device 601 may operate in a networked environmentsupporting connections to one or more remote computers, such ascomputing devices 641 and 651. In one example, the computing devices 641and 651 may be personal computers or servers that include many, or all,of the elements described above relative to the computing device 601.Specifically, the computing device 641 may represent one or moreelements of the remote environment 120 and computing device 651 mayrepresent one or more elements of the destination environment 140.Alternatively, computing device 641 and/or 651 may be a data store thatis affected by the operation of the computing device 601. The networkconnections depicted in FIG. 6 include a local area network (LAN) 625and a wide area network (WAN) 629, but may also include other networks.When used in a LAN networking environment, the computing device 601 isconnected to the LAN 625 through a network interface or adapter 623.When used in a WAN networking environment, the computing device 601 mayinclude a modem 627 or other means for establishing communications overthe WAN 629, such as the Internet 631. It will be appreciated that thenetwork connections shown are illustrative and other means ofestablishing a communications link between the computers may be used. Inone implementation, the various elements described in relation to theprotocol-agnostic file transfer apparatus 102 may be configured toaccept inbound networking communications and/or transfer outboundnetworking communications to one or more networking protocols. Thesenetworking protocols may include any of various well-known protocolssuch as TCP/IP, Ethernet, File Transfer Protocol (FTP), HypertextTransfer Protocol (HTTP), FTP over SSL (FTPS), HTTP over SSL (HTTPS),SSH File Transfer Protocol (SFTP), Secure Copy (SCP), Web DistributedAuthoring and Versioning (WebDAV), Secure Web Distributed Authoring andVersioning (WebDAVS), Trivial File Transfer Protocol (TFTP),Applicability Statement 2 (AS2), Odette File Transfer Protocol (OFTP),and Accelerated File Transfer Protocol (AFTP). Communication between oneor more of computing devices 601, 641, and/or 651 may be wired orwireless, and may utilize Wi-Fi, a cellular network, Bluetooth, infraredcommunication, or an Ethernet cable, among many others.

An application program 619 used by the computing device 601 according toan illustrative embodiment of the disclosure may includecomputer-executable instructions for invoking functionality related tothe machine learning training device 102. The computing device 601and/or the other devices 641 or 651 may also be mobile devices, such assmart phones, personal digital assistants (PDAs), and the like, whichmay include various other components, such as a battery, speaker, andantennas (not shown).

The disclosure is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the disclosure include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, and distributed computingenvironments that include any of the above systems or devices, and thelike.

The disclosure may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, and the like thatperform particular tasks or implement particular abstract data types.The disclosure may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked, for example, through a communications network. In adistributed computing environment, program modules may be located inboth local and remote computer storage media including memory storagedevices.

The present disclosures provide technical advantages. In oneimplementation, the mobile application development device 102 isconfigured to facilitate automated mobile application development thatutilizes reduced computational resources and reduces development timeand complexity by implementing a device that can receive applicationcode such as from App Code A 104, App Code B 106, and/or App Code C 108,and apply elements that are specific to one or more mobile operatingsystems on which the applications are intended to execute. Accordingly,the mobile application developer device 102 negates the need forpersonal developing one or more of the App Code A 104, App Code B 106,and/or App Code C 108 to be aware of the specific details of developmentfor one or more mobile operating systems and/or associated elements,such as security protocols, approved communication channels and thelike. In certain instances, the mobile application development device102 may utilize machine learning operations to facilitate automatedprocessing. Accordingly, the mobile application development device 102may be configured to process high volumes of information and executecomplex comparison algorithms and evaluations of different combinationscode elements.

The various embodiments described herein may be implemented bygeneral-purpose or specialized computer hardware. In one example, thecomputer hardware may comprise one or more processors, otherwisereferred to as microprocessors, having one or more processing coresconfigured to allow for parallel processing/execution of instructions.As such, the various disclosures described herein may be implemented assoftware coding, wherein those of skill in the computer arts willrecognize various coding languages that may be employed with thedisclosures described herein. Additionally, the disclosures describedherein may be utilized in the implementation of application-specificintegrated circuits (ASICs), or in the implementation of variouselectronic components comprising conventional electronic circuits(otherwise referred to as off-the-shelf components). Furthermore, thoseof ordinary skill in the art will understand that the variousdescriptions included in this disclosure may be implemented as datasignals communicated using a variety of different technologies andprocesses. For example, the descriptions of the various disclosuresdescribed herein may be understood as comprising one or more streams ofdata signals, data instructions, or requests, and physicallycommunicated as bits or symbols represented by differing voltage levels,currents, electromagnetic waves, magnetic fields, optical fields, orcombinations thereof.

One or more of the disclosures described herein may comprise a computerprogram product having computer-readable medium/media with instructionsstored thereon/therein that, when executed by a processor, areconfigured to perform one or more methods, techniques, systems, orembodiments described herein. As such, the instructions stored on thecomputer-readable media may comprise actions to be executed forperforming various steps of the methods, techniques, systems, orembodiments described herein. Furthermore, the computer-readablemedium/media may comprise a storage medium with instructions configuredto be processed by a computing device, and specifically a processorassociated with a computing device. As such the computer-readable mediummay include a form of persistent or volatile memory such as a hard diskdrive (HDD), a solid state drive (SSD), an optical disk (CD-ROMs, DVDs),tape drives, floppy disk, ROM, RAM, EPROM, EEPROM, DRAM, VRAM, flashmemory, RAID devices, remote data storage (cloud storage, and the like),or any other media type or storage device suitable for storing datathereon/therein. Additionally, combinations of different storage mediatypes may be implemented into a hybrid storage device. In oneimplementation, a first storage medium may be prioritized over a secondstorage medium, such that different workloads may be implemented bystorage media of different priorities.

Further, the computer-readable media may store softwarecode/instructions configured to control one or more of ageneral-purpose, or a specialized computer. Said software may beutilized to facilitate interface between a human user and a computingdevice, and wherein said software may include device drivers, operatingsystems, and applications. As such, the computer-readable media maystore software code/instructions configured to perform one or moreimplementations described herein.

Those of ordinary skill in the art will understand that the variousillustrative logical blocks, modules, circuits, techniques, or methodsteps of those implementations described herein may be implemented aselectronic hardware devices, computer software, or combinations thereof.As such, various illustrative modules/components have been describedthroughout this disclosure in terms of general functionality, whereinone of ordinary skill in the art will understand that the describeddisclosures may be implemented as hardware, software, or combinations ofboth.

The one or more implementations described throughout this disclosure mayutilize logical blocks, modules, and circuits that may be implemented orperformed with a general-purpose processor, a digital signal processor(DSP), an application-specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, or any conventionalprocessor, controller, microcontroller, or state machine. A processormay also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The techniques or steps of a method described in connection with theembodiments disclosed herein may be embodied directly in hardware, insoftware executed by a processor, or in a combination of the two. Insome embodiments, any software module, software layer, or threaddescribed herein may comprise an engine comprising firmware or softwareand hardware configured to perform embodiments described herein.Functions of a software module or software layer described herein may beembodied directly in hardware, or embodied as software executed by aprocessor, or embodied as a combination of the two. A software modulemay reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROMmemory, registers, hard disk, a removable disk, a CD-ROM, or any otherform of storage medium known in the art. An exemplary storage medium iscoupled to the processor such that the processor can read data from, andwrite data to, the storage medium. In the alternative, the storagemedium may be integral to the processor. The processor and the storagemedium may reside in an ASIC. The ASIC may reside in a user device. Inthe alternative, the processor and the storage medium may reside asdiscrete components in a user device.

In one aspect, this disclosure includes a mobile application developmentdevice that includes a platform processor. The platform processor may beconfigured to identify an application build element of an application indevelopment, identify and classify an application logic block portion ofthe application build element written in a platform-agnostic language,and identify a platform on which application is to be executed. Theplatform processor may further be configured to apply a platform-nativetemplate to the application logic block that is specific to the platformon which application is to be executed. The mobile applicationdevelopment device may further include a native application converterengine that is configured to identify logic features that are specificto the application to be built, and to extract the logic features as afirst set of tags associated with the application to be built. Thenative application converter engine may also be configured to identify asecond set of tags within the template applied by the platformprocessor, such that the second set of tags matches the first set oftags. The native application converter engine may further be configuredto replace the second set of tags with elements that are specific to theapplication to be built, and to provide a converted intermediarycodebase. The mobile application development device may also include amobile platform framework engine that is configured to add a common setof application features to the converted intermediary codebase, suchthat subsequent to the addition of the common set of applicationfeatures, the converted intermediary codebase is compiled and outputtedas the application.

The platform processor of the mobile application developer device mayadditionally include a library of code elements associated with theplatform on which the application is intended to run.

The platform on which the application is intended to run may be aspecific mobile operating system.

In one example, the identification of the logic features includesidentification of features within the application logic block.

In another example, the first set of tags identified security elementsand images.

The concept of application features includes one or more of a networksecurity feature, notification feature and a user interface feature.

The mobile application development device may also include anapplication compiler configured to compile and/or publish theapplication from the converted intermediary codebase.

In another example, the outputted application may be published using apublishing engine.

A mobile application development device may include a processor, and anon-transitory computer-readable medium comprising computer-executableinstructions that, when executed by the processor, are configured toidentify an application build element of an application in development,and identifying classify an application logic block portion of theapplication build element written in a platform-agnostic language. Thecomputer-executable instructions may further be configured to identify aplatform on which the application is to be executed, apply aplatform-native template to the application logic block that is specificto the platform on which the application is to be executed, identifylogic features that are specific to the application to be built, andextract the logic features as a first set of tags associated with theapplication to be built. The computer-executable instructions mayfurther include identification of a second set of tags within theapplied platform-native template that matches the first set of tags,replacing the second set of tags of elements that are specific to theapplication to be built to produce a converted intermediary codebase,and adding a common set of application features to the convertedintermediary codebase. In one example, subsequent to the addition of thecommon set of application features, the converted intermediary codebasemaybe compiled and outputted as the application.

The platform associated with mobile application development device maybe a specific mobile operating system.

The identification of the Lodge features may include identification offeatures within the application logic block.

In one example, the first set of tags identify security elements andimages.

In another example, the common set of application features include anetwork security feature, and notification feature, and a user interfacefeature.

The mobile application development device may additionally include anapplication compiler configured to compile and/or publish theapplication from the converted intermediary codebase.

The outputted application may be published using a publishing engine.

A method for mobile application development may include identifying anapplication build element of an application in development, identifyingand classifying application logic block portion of the application buildelement written in a platform-agnostic language, identifying a platformon which application is to be executed, applying a platform-nativetemplate of the application logic block that is specific to the platformon which the application is to be executed, identifying logic featuresthat are specific to the application to be built, and extracting thelogic features is a first set of tags associated with the application tobe billed. The method may additionally include identifying a second setof tags within the applied platform-native template that matches thefirst set of tags, replacing the second set of tags with elements thatare specific to the application to be billed to produce a convertedintermediary codebase, and adding a common set of application featuresto the converted intermediary codebase, such that subsequent to theaddition of the common set of application features, the convertedintermediary codebase is compiled and outputted as the application.

In another aspect, a mobile application development device includes aplatform processor. The platform processor may be configured to identifyan application build element of an application in development, identifyand classify an application logic block portion of the application buildelement written in a platform-agnostic language, and identify a platformon which application is to be executed. The platform processor mayfurther be configured to apply a platform-native template to theapplication logic block that is specific to the platform on whichapplication is to be executed. The mobile application developer devicemay further include a native application converter engine that isconfigured to identify logic features that are specific to theapplication to be built to extract the logic features as a first set oftags associated with the application to be built. The native applicationconverter engine may also be configured to identify a second set of tagswithin the template applied by the platform processor, such that thesecond set of tags matches the first set of tags. The native applicationconverter engine may further be configured to replace the second set oftags with elements that are specific to the application to be built, toprovide a converted intermediary codebase. The mobile applicationdevelopment device may also include a mobile platform framework enginethat is configured to add a common set of application features to theconverted intermediary codebase. The mobile platform framework enginemay further include an application data transformation processor that isconfigured to identify a communication request type, select anappropriate network channel to fulfill the communication request, andset up a communication session using the appropriate network channel toa requested destination.

The communication session may be obfuscated from a requester associatedwith the communication request type.

The communication request type may identify a source of the request as aweb browser or a mobile device.

The platform processor of the mobile application developer device mayadditionally include a library of code elements associated with theplatform on which the application is intended to run.

The platform on which the application is intended to run may be aspecific mobile operating system.

In one example, the identification of the logic features includesidentification of features within the application logic block.

In another example, the first set of tags identified security elementsand images.

The concept of application features includes one or more of a networksecurity feature, notification feature and a user interface feature.

The mobile application development device may also include anapplication compiler configured to compile and/or publish theapplication from the converted intermediary codebase.

In another example, the outputted application may be published using apublishing engine.

Accordingly, it will be understood that the invention is not to belimited to the embodiments disclosed herein, but is to be understoodfrom the following claims, which are to be interpreted as broadly asallowed under the law.

1. One or more non-transitory computer-readable media storinginstructions that, when executed by a computing platform comprising atleast one processor and memory, cause the computing platform to:classifying, for an application, an application logic block of anapplication build element written in a platform-agnostic language;applying a platform-native template to the application logic block thatis specific to a platform on which the application is to be executed;extracting at least one logic feature as a first set of tags associatedwith the application to be built; matching a second set of tags withinthe applied platform-native template with the first set of tags; andreplacing the second set of tags with elements that are specific to theapplication to be built to produce a converted intermediary codebase. 2.The one or more non-transitory computer-readable media of claim 1wherein the platform is a specific mobile operating system.
 3. The oneor more non-transitory computer-readable media of claim 1 wherein the atleast one logic feature comprises a feature within the application logicblock.
 4. The one or more non-transitory computer-readable media ofclaim 1 wherein the first set of tags identify security elements andimages.
 5. The one or more non-transitory computer-readable media ofclaim 1, wherein the instructions further cause the computing platformto: compile the application from the converted intermediary codebase. 6.A mobile application development device, comprising: a platformprocessor, configured to: classify, for an application, an applicationlogic block of an application build element written in aplatform-agnostic language; and apply a platform-native template to theapplication logic block that is specific to a platform on which theapplication is to be executed; and a native application converterengine, configured to: extract at least one logic feature as a first setof tags associated with the application to be built; match a second setof tags within the template applied by the platform processor with thefirst set of tags; and replace the second set of tags with elements thatare specific to the application to be built to produce a convertedintermediary codebase.
 7. The mobile application development device ofclaim 6, further comprising an application compiler configured tocompile the application from the converted intermediary codebase.
 8. Themobile application development device of claim 7, wherein the compiledapplication is published using a publishing engine.
 9. The mobileapplication development device of claim 8, wherein the publishing enginedeposits the application on a repository for subsequent accessing anddownloading by a mobile device.
 10. The mobile application developmentdevice of claim 6, wherein the platform processor comprises a library ofcode elements associated with the platform on which the application isintended to run.
 11. The mobile application development device of claim6, wherein the platform is a specific mobile operating system.
 12. Themobile application development device of claim 6, wherein the at leastone logic feature comprises a feature within the application logicblock.
 13. The mobile application development device of claim 6, whereinthe first set of tags identify security elements and images.
 14. Amethod for mobile application development, comprising: classifying, foran application, an application logic block of the application buildelement written in a platform-agnostic language; applying aplatform-native template to the application logic block that is specificto a platform on which the application is to be executed; extract atleast one logic feature as a first set of tags associated with theapplication to be built; matching a second set of tags within theapplied platform-native template with the first set of tags; andreplacing the second set of tags with elements that are specific to theapplication to be built to produce a converted intermediary codebase.15. The method of claim 14, further comprising: compiling the convertedintermediary codebase.
 16. The method of claim 15, further comprising:outputting the compiled converted intermediary codebase as theapplication.
 17. The method of claim 14, wherein the platform is aspecific mobile operating system.
 18. The method of claim 14, whereinthe at least one logic feature comprises a feature within theapplication logic block.
 19. The method of claim 14, wherein the firstset of tags identify security elements and images.
 20. The method ofclaim 14, further comprising: including a library of code elementsassociated with the platform on which the application is intended torun.